JMU JMU - Department of Computer Science
Help Tools
Examination Policies - The Final Exam


1 Structure

The final exam will consist of both a written portion and a computer-based programming portion. Both portions will be administered on the same day (during the time scheduled by the Registrar, listed at https://www.jmu.edu/registrar/students/examschedule.shtml).

You will have a total of 120 minutes to complete both portions of the exam. You may divide your time as you see fit, but it is probably in your best interest to attempt the written portion before the computer-based programming portion.

2 The Written Portion

2.1 Collaboration

The written portion of the final exam is "open book" but you must work entirely on your own.

2.2 Delivery

The written portion of the final exam will be delivered as a Canvas "quiz". It will become available (as an "assignment") at the scheduled exam start time and will remain available until the scheduled exam end time.

NOTE: Do not click on Submit Quiz until you have answered all of the questions to the best of your ability (i.e., until you are done). Canvas will automatically save your work. You can answer some questions, work on the computer-based portion, return to the written portion, and answer other questions (or change your answers), as long as you don't click on Submit Quiz.

3 The Computer-Based Programming Portion

3.1 Collaboration

The computer-based programming portion of the final exam is "open book" but you must work entirely on your own (without assistance from the instructor or teaching assistants). The source code you submit must be entirely your work; no part of it may be the work of anyone but you.

The source code you submit must be written entirely during the exam period. The use of any pre-existing code (other than that provided as part of the exam) will be considered a violation of the Honor Code.

3.2 Delivery

The computer-based programming portion of the final exam will be delivered as a Canvas "assignment". It will become available at the scheduled exam start time and will remain available until the scheduled exam end time.

3.3 Submission

All code must be submitted electronically using Autolab. Each question will have a distinct "Assignment" on Autolab (e.g., FEQ1 and FEQ2 under Final Exam). For each question, you must submit a .zip file containing just your .java files for that question. The .zip file must not contain any directories/folders (i.e., the .zip file must be organized as it has been for programming assignments).

No limit will be placed on the number of submissions but, obviously, you must complete the exam during the scheduled exam period and submissions waste time. So, you should write your code as if you will only have time to submit each question once or twice.

You should assume that Autolab will not provide "hints". In other words, the submission system will be "grading" your submissions not helping you debug them.

No submissions will be accepted after the end of the scheduled exam period. So, make sure you submit an answer for each question before the end of the scheduled exam period. Your last submission is the one that will be graded (so don't make spurious changes after your first submission -- such changes may lower your grade).

3.4 Grading

Your answers to some questions (though not all), will be verified by Autolab using multiple tests. Hence, if your code passes some tests but not others, it is possible to earn partial credit on some questions.

It is possible that your grade on the computer-based programming portion of an exam will be lower than the grade you receive from Autolab (if, for example, your code is poorly designed, poorly implemented, or inelegant). In other words, though style defects will not reduce your grade, other aspects of quality may.

It is also possible that your grade on the computer-based programming portion of an exam will be lower than the grade you receive from Autolab (if, for example, your code is correct but you submit it incorrectly).

4 Getting Help

I will be available during the scheduled meeting time via the normal course telepresence tool (at the "Office Hours" meeting code) and via email.

5 If Something Goes Wrong

If something goes wrong, don't panic. Try and record your work (e.g., by cutting and pasting into a word processing document or by taking a screen shot) and email it to me. If you are unable to record your work, still send me an email explaining the situation.

Copyright 2020